Migrating virtual asset

ABSTRACT

Embodiments include methods and devices for migrating virtual assets over networks that have a first manager connected to a physical host a virtual machine run. Aspects include registering the physical host to a second manager in the network, creating the mapping relationship of the physical host between a database of the first manager and a database of the second manager and importing instance data and status data of the virtual machine of the physical host from the database of the first manager into the database of the second manager. Aspects also include switching the management for the physical host from the first manager to the second manager.

DOMESTIC AND FOREIGN PRIORITY

This application is a continuation of U.S. patent application Ser. No.14/834,472, filed Aug. 25, 2015, which claims priority to Chinese PatentApplication No. 201410433277.3, filed Aug. 28, 2014, and all thebenefits accruing therefrom under 35 U.S.C. §119, the contents of whichin its entirety are herein incorporated by reference.

BACKGROUND

The present disclosure relates to networks and technology of cloudcomputing, and more specifically to a method and device for migratingvirtual assets over networks.

Migrating legacy virtual assets to cloud side is a key point for manycustomers who have started with virtual technology and want to changeand update to cloud. Motivations of cloud migration of general virtualasset mainly include: unifying resource management, that is, running aunified management system on a single platform; acquiring new featuresprovided by cloud technology, such as dynamic extension, highavailability, etc.; reusing legacy virtual assets, which have beencreated and used in existing cloud for a long time, in the newenvironment; and balancing workload across resource pools and so on.

A general method for cloud migration of virtual assets is to export avirtual machine (VM) instance, to convert it into an image file package,to transport (transfer) the file package, to import the file packageinto a target cloud computing platform (CCP), and to register and runthe VM instance on a physical host of the target CCP. Thus, the VM inthe source CCP may be migrated to the target CCP.

Types of cloud migration of virtual assets include: internal migrationthat VM is migrated between physical hosts in the same CCP; cross cloudmigration that VM is migrated between physical hosts in different CCPs;topo-based migration that a set of VMs with internal dependency aremigrated between different CCPs; and bundle-based migration that VMs andphysical hosts with internal dependency are migrated together betweendifferent CCPs.

Currently cross cloud migration of virtual assets includes shutting downthe VM, which may cause business disruptions. Furthermore, conversion ofVM file package needs a long time, transportation cost of the filepackage also depends on the network performance, and meanwhilecompatibility configuration for the new environment needs to beperformed by professionals. As a result, failure rate of migration isvery high.

SUMMARY

The present disclosure puts forward a new technical scheme for migratingvirtual assets, in which the management layer of for example a firstcomputing platform (manager) is migrated to the management layer of asecond computing platform, instead of migrating VMs and physical hostswith internal dependency on the first computing platform to the secondcomputing platform through a method of VM image transportation.

According to one aspect of the present disclosure, there is provided amethod for migrating virtual assets over networks having a first managerand a physical host connected, the physical host having a virtualmachine run thereon, the method includes: registering the physical hostto a second manager in the network; creating the mapping relationship ofthe physical host between a database of the first manager and a databaseof the second manager; importing instance data and status data of thevirtual machine of the physical host from the database of the firstmanager into the database of the second manager; and switching themanagement of the physical host from the first manager to the secondmanager

According to another aspect of the present disclosure, there is provideda device for migrating virtual assets over networks, having a firstmanager and a physical host connected, the physical host having avirtual machine run thereon, the device comprising: a registrationmodule configured to register the physical host to a second manager inthe network; a mapping module configured to create the mappingrelationship of the physical host between a database of the firstmanager and a database of the second manager; an instance conversionmodule configured to import instance data and status data of the virtualmachine of the physical host from the database of the first manager intothe database of the second manager; and a redirection module configuredto switch the management of the physical host from the first manager tothe second manager.

With the method and device for migrating virtual assets of the presentdisclosure, the business disrupt seldom occurs during migration, VM doesnot need to be converted to a file package, and there is notransportation of the VM file package and hardware position changeeither. This keeps the basic configuration of legacy virtual assets suchas physical host, VM, network and so on, and it is easy to realizeautomated process.

BRIEF DESCRIPTION OF THE DRAWINGS

Through the more detailed description of exemplary embodiments of thepresent disclosure in combination with the accompanying drawings, theabove and other objects, features and advantages of the presentdisclosure will become more apparent, wherein the same referencegenerally refers to the same components in the exemplary embodiments ofthe present disclosure.

FIG. 1(a) represents a cloud computing node according to one embodimentof the present disclosure.

FIG. 1(b) represents the cloud computing environment according to oneembodiment of the present disclosure.

FIG. 1(c) represents an abstract model layer according to one embodimentof the present disclosure.

FIG. 2 shows a basic topology of a cloud side applied in the presentdisclosure.

FIG. 3 shows a block diagram of a device for migrating virtual assetsover networks according to one embodiment of the present disclosure.

FIG. 4 is a diagram showing that a second manager is established in thenetwork with a first manager.

FIG. 5 is a diagram showing that a physical host is re-registeredaccording to an embodiment of the present disclosure.

FIG. 6 is a diagram showing that VM instance data are convertedaccording an embodiment of the present disclosure.

FIG. 7 is a diagram showing that a physical host and a VM are redirectedaccording an embodiment of the present disclosure.

FIG. 8 is a flowchart showing a method for migrating virtual assetsaccording an embodiment of the present disclosure.

DETAILED DESCRIPTION

Exemplary embodiments will be described in more detail with reference tothe accompanying drawings, in which the preferable embodiments of thepresent disclosure have been illustrated. However, the presentdisclosure can be implemented in various manners, and thus should not beconstrued to be limited to the embodiments disclosed herein. On thecontrary, those embodiments are provided for the thorough and completeunderstanding of the present disclosure, and completely conveying thescope of the present disclosure to those skilled in the art.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1(a), a schematic of an example of a cloudcomputing node is shown. Cloud computing node 10 shown in FIG. 1(a) isonly one example of a suitable cloud computing node and is not intendedto suggest any limitation as to the scope of use or functionality ofembodiments of the invention described herein. Regardless, cloudcomputing node 10 is capable of being implemented and/or performing anyof the functionality set forth hereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1(a), computer system/server 12 in cloud computing node10 is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 22. Still yet, computer system/server 12 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 20. As depicted, network adapter 20communicates with the other components of computer system/server 12 viabus 18. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 12. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 1(b), illustrative cloud computing environment 50is depicted. As shown, cloud computing environment 50 comprises one ormore cloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 2 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 1(c), a set of functional abstraction layersprovided by cloud computing environment 50 (FIG. 1(b)) is shown. Itshould be understood in advance that the components, layers, andfunctions shown in FIG. 3 are intended to be illustrative only andembodiments of the invention are not limited thereto. As depicted, thefollowing layers and corresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes, in oneexample IBM® zSeries® systems; RISC (Reduced Instruction Set Computer)architecture based servers, in one example IBM pSeries® systems; IBMxSeries® systems; IBM BladeCenter® systems; storage devices; networksand networking components. Examples of software components includenetwork application server software, in one example IBM WebSphere®application server software; and database software, in one example IBMDB2® database software. (IBM, zSeries, pSeries, xSeries, BladeCenter,WebSphere, and DB2 are trademarks of International Business MachinesCorporation registered in many jurisdictions worldwide).

Virtualization layer 62 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer 64 may provide the functions describedbelow. Resource provisioning provides dynamic procurement of computingresources and other resources that are utilized to perform tasks withinthe cloud computing environment. Metering and Pricing provide costtracking as resources are utilized within the cloud computingenvironment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal provides access to the cloud computing environment forconsumers and system administrators. Service level management providescloud computing resource allocation and management such that requiredservice levels are met. Service Level Agreement (SLA) planning andfulfillment provide pre-arrangement for, and procurement of, cloudcomputing resources for which a future requirement is anticipated inaccordance with an SLA.

Workloads layer 66 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation; software development and lifecycle management; virtualclassroom education delivery; data analytics processing; transactionprocessing; and virtual asset migration.

In the following, several terms which may be used in the specificationare explained as follows.

Cloud (or cloud side): it consists of a cloud management platform, aphysical host managed by the cloud management platform and a VM run onthe physical host connected over network.

Cloud computing platform: it is the cloud management platform of entirecloud side, and is used for performing cloud processing such as storingand/or computing, etc. and issuing various instructions to the physicalhost managed by it. It may also be referred to as “manager” or “cloudmanager”.

Physical host: it is connected with the cloud manager over network, itis the host machine of a VM, receives various instructions of the cloudmanager through a controller agent so as to run, change or stop a VMapplication thereon, and reports the processing result to the cloudmanager.

Virtual Machine (VM): it is an application run on the physical host andmay complete various tasks and functions so as to provide cloudservices. The above explanation is only exemplary and do not limit thescope of the present disclosure.

FIG. 2 shows a basic topology of a cloud side applied in the presentdisclosure. The basic topology of the cloud side 200 applied in thepresent disclosure includes a cloud manager 201, a database 202 of thecloud manager 201, physical hosts 203 and 204 which may be multiple,multiple VMs 205 and 206 which are run on physical hosts so as toprovide cloud services, and network 210 which connects the cloud manager201 and physical hosts 203 and 204 and connects the cloud side 200 withthe external network so as to provide the access service.

FIG. 3 shows a block diagram of a device for migrating virtual assetsover networks according to one embodiment of the present disclosure.

As shown in FIG. 3, the present disclosure provides a device formigrating virtual assets over networks. In the following, in embodimentsof the present disclosure, the above device for migrating virtual assetsis represented by a cloud redirector (CR) 320. The cloud side 200according to an embodiment of the present disclosure has a manager(which may be referred to as “first manager” or “source manager” below,and may also be referred to as “first cloud manager” or “source cloudmanager” since it refers to the cloud manager of virtual assets beforemigration) 201, physical hosts 203 and 204 which are managed by thefirst cloud manager 201, connected over the network 210, and VMs 205 and206 run on the physical hosts 203 and 204. The cloud redirector 320according to an embodiment of the present disclosure is also connectedto a second manager (which may be referred to as “second cloud manager”or “target manager”, and may also be referred to as “target cloudmanager” since it is the destination where the virtual assets are to bemigrated) 302.

The cloud redirector 320 according to an embodiment of presentdisclosure includes: a registration module 321 configured to registerthe physical hosts 203 and 204 to the second cloud manager 302 in thenetwork 210, a mapping module 322 configured to create the instancemapping relationship of the physical hosts 203 and 204 between thedatabase 202 of the first cloud manager 201 and the database 303 of thesecond cloud manager 302, an instance conversion module 323 configuredto import, based on the created mapping relationship, instance data andstatus data of VMs of the physical host 203 and 204 from the database202 of the first cloud manager 201 into the database 303 of the secondcloud manager 302, and a redirection module 324 configured to switch themanagement of the physical hosts 203 and 204 from the first cloudmanager 201 to the second cloud manager 302.

The cloud redirector 320 according to an embodiment of presentdisclosure may further include (the following units are not shown in thefigure) a Central Processing Unit (CPU) for executing related programsto process various data and control operations of respective components(units) in the cloud redirector 320, a Read Only Memory (ROM) forstoring various programs required for performing various process andcontrol by the CPU, a Random Access Memory (RAM) for storingintermediate data temporarily produced in the procedure of process andcontrol by the CPU, an Input/Output (I/O) component for connecting withexternal devices so as to transport various data between the externaldevices and the cloud redirector 320 according to an embodiment ofpresent disclosure, and user interface (I/F) components including akeyboard, a mouse, a touch pad and other components which may beimplemented by various display apparatuses or voice apparatuses toperform interaction with users. These apparatuses or components arecoupled with the registration module 321, the mapping module 322, theinstance conversion module 323, the redirection module 324 and so on inthe cloud redirector 320 via data bus and/or control bus to performvarious controls and related operations, so as to realize variousfunctions of the present disclosure to provide cloud services.

According to one embodiment of present disclosure, functions of theregistration module 321, the mapping module 322, the instance conversionmodule 323, the redirection module 324 may also be implemented by thatprograms are stored in ROM and executed in CPU to complete respectivefunctions. According to one embodiment of present disclosure, respectiveapparatus, modules and units in the cloud redirector 320 may also beimplemented by being combined as one component, and their specificimplementation does not limit the scope of the present disclosure.

According to one embodiment of present disclosure, the cloud redirector320 may be implemented by running a computer program in the exemplarycomputer system/server 12 as shown in FIG. 1. In the following, theoperation to realize cloud migration of virtual assets of the cloudredirector 320 according to an embodiment of present disclosure will bedescribed in detail.

The cloud redirector 320 according to the present disclosure extractsvarious information of the first cloud manager 201, including thesoftware name, the version number, the ip address, the mac address, thenetwork configuration parameters, the user name and password of thefirst cloud manager 201, as well as the user name and password of thedatabase of the first cloud manager 201 and so on. Meanwhile, the cloudredirector 320 further extracts the topology information of the firstcloud manager 201, such as the number (although there are shown twophysical hosts in the specification, there may be more or less physicalhosts as needed in an actual system) of physical hosts 203 and 204managed by the first cloud manager 201, and the number (there are shownthree VMs on each physical host in the specification, more or less VMsmay be run as needed in an actual system) of VMs 205 and 206 on eachphysical host and so on. The above information data may for example beextracted from the first cloud manager 201 by running a script file inthe cloud redirector 320. The above extracted information data areenrolled (registered) in the cloud redirector 320.

FIG. 4 is a diagram showing that a second cloud manager is establishedin the network with a first cloud manager. As shown in FIG. 4, the cloudredirector 320 according to the present disclosure is connected to thenetwork 210, and includes a module for establishing a new server in thenetwork 210, a module for installing the second cloud manager 302 on thenew server 210 and a module for starting the second cloud manager 302.

The module for establishing the new server in the network 210establishes a new target server 430 in the network 210 where the firstcloud manager 201 is located. This operation may be realized by adding anew physical server in the network 210. According to one embodiment ofthe present disclosure, the above added new physical server 430 may beimplemented by the exemplary computer system/server 12 as shown in FIG.1(a).

The module for installing the second cloud manager 302 on the new server210 installs the second cloud manager 302 in the newly added targetserver 430. The second cloud manager 302 may be a software program andrealizes the function of managing physical hosts and VMs run on thephysical hosts by being installed on the new server 430. According toone embodiment of present disclosure, the second cloud manager 302 mayalso be a physical hardware device and realizes the correspondingfunctions by connecting to the network 210. The module for starting thesecond cloud manager 302 starts the second cloud manager 302 on thetarget server 430.

The cloud redirector 320 according to the present disclosure extractsvarious information of the second cloud manager 302, including thesoftware name, the version number, the ip address, the mac address, thenetwork configuration parameters, the user name and password of thesecond cloud manager 302, as well as the version information, the username and password of the database of the second cloud manager 302 and soon, and enrolls them in the cloud redirector 320. At this time, sincethe newly started second cloud manager 302 has not managed any physicalhost and VM, the cloud redirector 320 does not extract the topologyinformation of the second cloud manager 302. The above information datamay for example be extracted from the second cloud manager 302 berunning a script file in the cloud redirector 320.

The cloud redirector 320 according to the present disclosure may furtherinclude a module for extracting the installation package of thecontroller agent and its configuration information from the second cloudmanager 302. The module extracts the installation package of thecontroller agent and its configuration information from the second cloudmanager 302, and stores them in the cloud redirector 320. Here, thecontroller agent may be a software program which may receive, by runningin a physical host, various instructions from the second cloud manager,manage physical hosts and return the resulting data to the second cloudmanager.

According to one embodiment of present disclosure, the registrationmodule 321 is further configured to stop the management service of thefirst cloud manager 201, to install the controller agent of the secondcloud manager 302 on the physical hosts 203 and 204, and to configureand run the controller agent so as to register (the identificationinformation of) the physical hosts 203 and 204 to the second cloudmanager 302.

According to another embodiment of present disclosure, the pre-storageposition of the installation package of the controller agent and itsconfiguration information does not limit the technical scope of thepresent disclosure. They may also be stored in any other device than thesecond cloud manager 302, for example, may be pre-stored in the cloudredirector 320 or the physical hosts 203 and/or 204, only if theinstallation package of the controller agent and its configurationinformation exist on the physical hosts 203 and 204 before thecontroller agent is installed on the physical hosts 203 and 204.

FIG. 5 is a diagram showing that a physical host is re-registeredaccording to an embodiment of the present disclosure. Specifically, asshown in FIG. 5, at operation {circle around (1)}, the managementservice of the first cloud manager 201 is stopped; at operation {circlearound (2)}, the cloud redirector 320 installs controller agents of thesecond cloud manager 302 on as-is physical hosts 203 and 204 of thefirst cloud manager 201; and at operation {circle around (3)}, the cloudredirector 320 configures and runs these controller agents and registersthe as-is physical hosts 203 and 204 to the second cloud manager 302over the network 210. The order relationship of the above operations{circle around (1)}, {circle around (2)} and {circle around (3)} do notlimit the scope of the present disclosure. According to anotherembodiment of present disclosure, the operations {circle around (1)},{circle around (2)} and/or {circle around (3)} may be performedsimultaneously. Alternatively, the operations {circle around (2)} and/or{circle around (3)} may be performed firstly, and the operation {circlearound (1)} is then performed.

More specifically, the operation that the as-is physical hosts 203 and204 are registered to the second cloud manager 302 is completed byconfiguring and running controller agents of the second cloud manager onthe physical hosts 203 and 204. After the controller agents of thesecond cloud manager 302 are installed to the physical hosts 203 and 204via the cloud redirector 320 of the present disclosure and areconfigured and run in accordance with the information (the ip address,the communication port “port”, the authentication information, etc) ofthe second cloud manager 302, the controller agents will establish thecommunication connection with the server of the second cloud manager 302automatically, and transmits the information (which is decidedspecifically by the design of the second cloud manager 302) of thephysical hosts 203 and 204 collected by them to the server of the secondcloud manager 302. Thus, registration is completed. In this way, in thedatabase of the second cloud manager 302, the physical host data tablewill generate a piece of information record regarding the registeredphysical host. In general, the collected information of the physicalhost mainly includes: the CPU information, the memory information, thedisk storage information, the system type, the ip address, the macaddress, the host name, etc. Meanwhile, an ID will be assigned or aglobally-unique identification information “guid” will be produced foreach physical host in a host storage table. The ID/guid will be referredto by other tables so as to associate with the physical host. Forexample, in a VM list, for a VM, an attribute such as host_id (ID/guidof the physical host is stored therein) is used to identify to whichphysical host the VM belongs.

According to one embodiment of present disclosure, the mapping module322 is further configured to extract the identity information of thephysical hosts 203 and 204, to locate, based on the identityinformation, the related records of the physical hosts 203 and 204 inthe databases 202 and 303 of both the first cloud manager 201 and thesecond cloud manager 302, and to create the instance mappingrelationship of the physical hosts 203 and 204 between the database 202of the first cloud manager 201 and the database 303 of the second cloudmanager 302 according to the located records. Here, the identityinformation includes at least one of the ip address, mac address, hostname, ID, guid, etc as described above. Here, the related records referto records including information on the physical hosts 203 and 204, inthe databases 202 and 303, such as the configuration information, andthe instance data and status data of related VMs.

Specifically, as shown in FIG. 5, at operation {circle around (4)}, thecloud redirector 320 searches the physical hosts 203 and 204 for theiridentity information, for example, host names, ip addresses, macaddresses, ids, guids, etc of the physical hosts 203 and 204; atoperation {circle around (5)}, by using the searched identityinformation of the physical hosts 203 and 204, records related with thephysical hosts 203 and 204 are extracted from the database 202 of thefirst cloud manager 201 and the database 303 of the second cloud manager302; the above extraction of related records may also be the locating ofrecords of the physical hosts 203 and 204 in the database 202 and thelocating of records of the physical hosts 203 and 204 in the database303; at operation {circle around (6)}, in the cloud redirector 320, themapping relationship of as-is physical hosts 203 and 204 between thedatabase 202 of the first cloud manager 201 and the database 303 of thesecond cloud manager 302, for example, but not limited to, a mappingtable M, is established.

According to one embodiment of present disclosure, the mapping table Mis for establishing the association of physical host instances betweentwo databases, that is, associating the id of a physical host in theas-is cloud manager with the id of the physical host in the target cloudmanager. Therefore, the information in the mapping table M mainlyincludes the information capable of uniquely identifying the physicalhost in the two cloud managers. An example is shown as follows:

TABLE Physical_Machine_Mapping ( hostname,//host name of a physical hostip,//IP address of the physical host mac,//Mac address of the physicalhost source_id,//ID of the physical host in the as-is cloud managementplatform target_id,//ID of the physical host in the target cloudmanagement platform source_table,//host table name of the physical hostin the as-is cloud management platform target_table,//host table name ofthe physical host in the target cloud management platformsource_guid,//globally-unique identifier of the physical host in theas-is cloud management platform target_guid,//globally-unique identifierof the physical host in the target cloud management platform)

According to one embodiment of present disclosure, the above exemplarymapping table M is only one of examples for realizing the mappingrelationship of the present disclosure, which does not limit the scopeof the present disclosure.

According to one embodiment of present disclosure, the instanceconversion module 323 further includes a module for stopping thecontroller agents of the first cloud manager 201 on the physical hosts203 and 204, a module for stopping the management service of the secondcloud manager 302, a module for extracting the information data of thephysical hosts 203 and 204 as well as the instance data and the statusdata of their VMs from the database 202 of the first cloud manager 201according to the mapping relationship (for example the mapping table M),a module for extracting the information data of the physical hosts 203and 204 from the database 303 of the second cloud manager 302 as thedocked point data according to the mapping relationship (for example themapping table M), a module for converting the instance data and thestatus data of the database 202 of the first cloud manager 201 into theinstance data and the status data of the database 303 of the secondcloud manager 302 according to predefined metadata mapping in databases,and a module for importing the converted instance data and the statusdata into the database 303 of the second cloud manager 302 by using thedocked point data. Here, the above docked point data refer to the indexdata which exist in both the databases 202 and 203 and associate theinformation data of the physical hosts 203 and 204 in the two databases202 and 203 with each other.

FIG. 6 is a diagram showing that VM instance data are convertedaccording an embodiment of the present disclosure. As shown in FIG. 6,at operation {circle around (1)}, the cloud redirector 320 extracts thedata (for example data of the identity information and configurationinformation and so on) of the physical hosts 203 and 204 as well as theinstance data and the status data of VMs 205 and 206 run thereon fromthe database 202 of the first cloud manager 201 according to theinstance mapping relationship (for example the mapping table M). Atoperation {circle around (2)}, the cloud redirector 320 extracts thedata (for example data of the identity information and configurationinformation and so on) of the physical hosts 203 and 204 from thedatabase 303 of the second cloud manager 302 according to the instancemapping relationship (for example the mapping table M). At operation{circle around (3)}, the instance data and the status data of VMs 205and 206 on the physical hosts 203 and 204 are reconstructed in thedatabase 303 of the second cloud manager 302 according to the predefinedmetadata mapping in databases, that is, the instance data and the statusdata of VMs 205 and 206 of the physical hosts 203 and 204 in thedatabase 202 of the first cloud manager 201 are converted into theinstance data and the status data thereof in the database 303 of thesecond cloud manager 302.

More specifically, in FIG. 6, the management data for the physical hosts203 and 204 in the first cloud manager 201 are grafted into the databaseof the second cloud manager 302. For example, the following operationsmay be performed: 1. the controller agents of the first cloud manager201 are stopped on the physical hosts 203 and 204; 2. the managementservice of the second cloud manager 302 is stopped; 3. the database 202of the first cloud manager 201 is accessed, and the data of the physicalhosts 203 and 204 as well as the instance data and the status data ofVMs are extracted according to the mapping relationship (for example themapping table M); 4. The database 303 of the second cloud manager 302are accessed, and the data of the mapped physical hosts 203 and 204 areextracted as the docked point data according to the mapping relationship(for example the mapping table M); 5. the VM instance data and statusdata in the database 202 of the first cloud manager 201 are convertedinto the VM instance data and status data in the database 303 of thesecond cloud manager 302 by using the predefined metadata mapping; 6.The converted VM instance data and status data imported into thedatabase 303 of the second cloud manager 302 by referring to the abovedocked point data. The above operations may be completed bycorresponding modules in the instance conversion module 323.

According to one embodiment of present disclosure, the redirectionmodule 324 further includes a module for starting the management serviceof the second cloud manager 302, a module for starting controller agentsof the second cloud manager 302 on the physical hosts 203 and 204, amodule for verifying the status of the second cloud manager 302, and amodule for removing the controller agents of the first cloud manager 201from the physical hosts 203 and 204.

FIG. 7 is a diagram showing that a physical host and a VM are redirectedaccording an embodiment of the present disclosure. As shown in FIG. 7,at operation {circle around (1)}, the cloud redirector 320 starts themanagement service of the second cloud manager 302, and startscontroller agents of the second cloud manager 302 on the physical hosts203 and 204. At operation {circle around (2)}, the status of the secondcloud manager 302 is verified. For example, the status of the secondcloud manager 302 may be verified by establishing VMs on the physicalhosts 203 and 204 and starting or stopping VMs or by refreshing statusesof the physical hosts 203 and 204. At operation {circle around (3)}, thecloud redirector 320 removes controller agents of the first cloudmanager 201 from the physical hosts 203 and 204.

According to one embodiment of present disclosure, the cloud redirector320 further includes a module for starting the management service of thefirst cloud manager 201. As shown in FIG. 7, at operation {circle around(4)}, the cloud redirector 320 re-starts the management service of thefirst cloud manager 201. In this way, after a part of virtual assets ofthe first cloud manager 201 have been migrated to the second cloudmanager 302, the first cloud manager 201 may still continue running soas to manage the other remaining virtual assets which are not migrated.

According to one embodiment of present disclosure, before the technicalscheme of the present disclosure are implemented, it is in generalrequired to create the metadata mapping between a first cloud managertype and a second cloud manager type in a database by a technicalperson. The metadata mapping in the present disclosure refers toestablishing the metadata correspondence between databases of the firstcloud manager and the second cloud manager according to database typesof the both, for example, the two databases may have a common index andso on, so that data in one database may be found by the correspondingdata in another database.

According to one embodiment of present disclosure, before the technicalscheme of the present disclosure are implemented, it is in generalrequired to check in advance whether the environment for performing thecloud migration meets some pre-requisites, and customers need to inputsome information to support such check and judgment. For example, thesepre-requisites may be, but not limited to: 1. The cloud migration to beperformed should be able to support the type of the first cloud managerand the type of the second cloud manager; 2. For VMs to be migrated, thephysical hosts running them should be supported by both the first cloudmanager and the second cloud manager, and only if so, the as-is physicalhost of the first cloud manager and VMs run thereon can be migrated tothe second cloud manager; 3. The cloud redirector should be able toaccess physical hosts and databases of cloud managers directly,accessing physical hosts and cloud managers directly can support thatthe cloud redirector switches the management chain between the firstcloud manager and the second cloud manager, for example, “SSH” or keyfile are used to manage the configuration of physical hosts, andaccessing databases of the first cloud manager and the second cloudmanager directly can support migration of the instance data and thestatus data of VMs; 4. Attributes (e.g. host types, configuration items,function definitions, etc) of database of the first cloud manager anddatabase of the second cloud manager should be able to be mapped witheach other, which can be realized by an expert establishing predefinedmetadata mapping of the database level before the cloud migration; 5.There is no configuration conflict between agents of the first cloudmanager and agents of the second cloud manager; 6. There is no need tochange physical hosts running VMs or the network.

According to another embodiment of present disclosure, it is alsopossible to acquiesce that these pre-requisites are met instead ofchecking whether the environment where the cloud migration is performedmeets these pre-requisites in advance. In this way, in a case that anactual environment of cloud migration has met these pre-requisites, itis not necessary to perform such checking in advance.

Furthermore, according to one embodiment of present disclosure, whendisposing the cloud redirector 320 according to an embodiment of thepresent disclosure, it is required to verify the cloud redirector 320′accesses to the physical hosts 203 and 204 as well as the first cloudmanager 201 and the second cloud manager 302. The public (secure shellprotocol) SSH key of the cloud redirector 320 is disposed, or user namesand passwords of physical hosts and/or cloud managers for verificationare collected, so that these physical hosts and cloud managers can beaccessed directly. Here, SSH is a protocol for providing secure remotelogin and other secure network services on an unsecured network.

FIG. 8 is a flowchart showing a method for migrating virtual assetsaccording an embodiment of the present disclosure. In the method formigrating virtual assets according to an embodiment of the presentdisclosure, the cloud side has a first manager, physical hosts and VMsrunning on the physical hosts which are connected over networks. Asshown in FIG. 8, at block S801, physical hosts are registered to asecond manager in the network where the first manager is located. Atblock S802, the mapping relationship of physical hosts between thedatabase of the first manager and the database of the second manager iscreated. At block S803, instance data and status data of VMs of physicalhosts in the database of the first manager are imported into thedatabase of the second manager. At block S804, the management ofphysical hosts is switched from the first manager to the second manager.

According to one embodiment of present disclosure, the above methodfurther includes blocks of setting up a new server in the network,installing the second manager on the new server and starting the secondmanager. According to one embodiment of present disclosure, the abovemethod further includes blocks of extracting the installation package ofa controller agent and its configuration information from the secondmanager, the controller agent is used to receive instructions from thesecond manager and to return the result to the second manager.

According to one embodiment of present disclosure, in the above method,the block of registering physical hosts to the second manager in thenetwork includes: stopping the management service of the first manager;installing the controller agent of the second manager on physical hosts;configuring and running the controller agent so as to register thephysical hosts to the second manager. In the above embodiment, the blockof stopping the management service of the first manager and the block ofinstalling the controller agent of the second manager on the physicalhosts may be performed simultaneously, or may be performed in a reverseorder. The order of performing them does not limit the scope of thepresent disclosure.

According to one embodiment of present disclosure, in the above method,the block of creating the mapping relationship of physical hostsincludes blocks of extracting the identity information of physicalhosts, locating the records related to the physical hosts in databasesof both the first manager and the second manager based on the identityinformation, and establishing the mapping relationship of the physicalhosts in the two databases according to the located records, in whichthe identity information includes at least one of the ip address, macaddress, the host name, id and guid.

According to one embodiment of present disclosure, in the above method,the block of importing instance data and status data of VMs of physicalhosts from the database of the first manager into the database of thesecond manager includes blocks: stopping the controller agent of thefirst manager on physical hosts; stopping the management service of thesecond manager; extracting information data of physical hosts as well asinstance data and status data of VMs thereof from the database of thefirst manager based on the mapping relationship; extracting informationdata of physical hosts from the database of the second manager based onthe mapping relationship, in which information data of physical hostsextracted from the database of the second manager are taken as dockedpoint data; converting instance data and status data of the database ofthe first manager into instance data and status data of the database ofthe second manager according to predefined metadata mapping indatabases; and importing the converted instance data and status datainto the database of the second manager by referring to the docked pointdata.

According to one embodiment of present disclosure, in the above method,the block of switching the management for physical hosts from the firstmanager to the second manager includes blocks of starting the managementservice of the second manager, starting the controller agent of thesecond manager on the physical hosts, verifying the status of the secondmanager, and removing the controller agent of the first manager from thephysical hosts.

According to one embodiment of present disclosure, the above methodfurther includes a block of starting the management service of the firstmanager. In the above, respective embodiments according to the presentdisclosure are described in combination with attached drawings. Thepresent invention may be a system, a method, and/or a computer programproduct. The computer program product may include a computer readablestorage medium (or media) having computer readable program instructionsthereon for causing a processor to carry out aspects of the presentinvention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational blocks to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed is:
 1. A method for migrating virtual assets over anetwork having a first manager and a physical host connected, thephysical host having a virtual machine run thereon, the methodcomprising: registering the physical host to a second manager in thenetwork; creating a mapping relationship between the physical hostbetween a database of the first manager and a database of the secondmanager; importing instance data and status data of the virtual machineof the physical host from the database of the first manager into thedatabase of the second manager; switching management for the physicalhost from the first manager to the second manager, wherein creating themapping relationship of the physical host comprises: extracting theidentity information of the physical host; locating a record of thephysical host in the databases of both the first manager and the secondmanager based on the identity information; and establishing the mappingrelationship of the physical host in the two databases according to thelocated record.
 2. The method according to claim 1, further comprising:setting up a new server in the network; installing the second manager onthe new server; and starting the second manager.
 3. The method accordingto claim 2, wherein registering the physical host to the second managerin the network comprises: stopping management service of the firstmanager; installing a controller agent of the second manager on thephysical host; and configuring and running the controller agent so as toregister the physical host to the second manager.
 4. The methodaccording to claim 3, further comprising extracting an installationpackage of the controller agent and the configuration informationthereof from the second manager, the controller agent used for receivinginstructions from the second manager and returning the result to thesecond manager.
 5. The method according to claim 1, wherein importinginstance data and status data of the virtual machine of the physicalhost from the database of the first manager into the database of thesecond manager comprises: stopping a controller agent of the firstmanager on the physical host; stopping the management service of thesecond manager; extracting information data of the physical host as wellas instance data and status data of its virtual machine from thedatabase of the first manager based on the mapping relationship;extracting information data of the physical host from the database ofthe second manager based on the mapping relationship, the informationdata extracted from the database of the second manager taken as dockedpoint data; converting the instance data and status data in the databaseof the first manager into the instance data and status data in thedatabase of the second manager according to pre-defined metadata mappingin the databases; and importing the converted instance data and statusdata into the database of the second manager by means of the dockedpoint data.
 6. The method according to claim 1, wherein switching themanagement for the physical host from the first manager to the secondmanager comprises: starting the management service of the secondmanager; starting a controller agent of the second manager on thephysical host; verifying the state of the second manager; and removing acontroller agent of the first manager from the physical host.